Originally by: Tarminic

---

1. Concord destroys missiles in flight, I believe
2. He got CONCORDED because he fired on you. End of story.
3. You were shield-repping someone being CONCORDED, which could be used as an exploit to avoid losing your ship to concord, therefore you received a firm CONCORDOKKEN. What exactly are you complaining about?

---

Originally by: Cdr Foxbat

---

That one has been around for years................

Problem is its hard to tell if you are repping a friend who accidently shot YOU, or repping a friend who intentionaly shot someone else and wants to remote tank concord.

Any change would have the high sec NPC hunters using and abusing it: "shield rep my ship!!!" then opening fire on the poor guy that helped them.......

---

Originally by: Midarin

---

Originally by: PHPR Ronin

---

Step 3) He had auto-target back on (normally no big deal)

---

Very dangerous setting. Do not use.

Quote:

---

Step 4) game client was glitched and his missle launcher was apperently set to auto-fire

---

It's not a glitch. We call this "cycling" your weapons and modules. If you turn on a module but it can't actually come on (most commonly because the target is out of range or completely off grid) it will stay on until you target something else at which point it comes on automatically, or until there is a session change like jumping through a gate or docking at which point the modules go back to normal.

You can use this to your advantage when fighting. Click on all the relevant weapons and other modules and then click in your overview or in space on some object that is way off grid (like a far away gate). Then when your target appears, you just start targeting him like normal. As soon as you have a lock, all cycled modules instantly turn on your target at once.

---

Originally by: OneSock

---

Seems a bit daft to me. If you've joined a gang with someone you resign all rights to concord protection. You've effectively entered into a trusted relationship and can shoot each other at will regardless.

At least that's how I'd code it.

---

Originally by: WulfWestphal

---

Edited by: WulfWestphal on 09/07/2007 12:15:29

Originally by: PHPR Ronin

---

The problem lies that I was shield repping him before he became a criminal. I should have been given a chance to shut down my reppers before i was also flagged. Maybe an automatic shutdown "Sheild rep module has been deactived because your target is now a global criminal" or perhaps a message stating "if you continue to shield rep %playername% then you will be flagged as a criminal"

---

... how many more warning messages do you want to get? is it too much to use your brain to avoid beeing shot down by concord? it is said more then one times (ingame too) that you get criminal status when you repair a criminal. if your friend shot that missile due to lag or whatever, well thats bad luck. you could've tried to shut down the repper after you saw that your friend shot.

anyhow: the rules are clear, there is no need for a million additional warning messages for the lazy folks. there is also no need that the game does thinking for you to switch off the repper. use your brain.

edit: the threadtitel is of utter stupidity.

---

Originally by: Lucre

---

So what you're basically saying is that you were CONCORDOKKEN'D for aiding and abetting an attack on yourself...?

That's a neat trick!

Then again, suicide used to be illegal in RL (may well still be in some countries or states). It doesn't have to make sense, it's the law!

---

Originally by: Tortun Nahme

---

Originally by: PHPR Ronin

---

The problem lies that I was shield repping him before he became a criminal.

---

therein lies the flaw in your logic

you didnt get concorded for the rep cycle/cycles that took place BEFORE he fired, however any new cycles after that count as new module activations, DO NOT have remote repair/transports set on autorepeat

---

Originally by: Tarazed Aquilae

---

Maybe there are ways to avoid things like this. Maybe you donÆt need to remote repair people in missions. Maybe itÆs really funny when it happens.

But still, the CONCORD system is just screwy right now and it needs some work. IÆm not sure what kind of work it needs exactly, I just know itÆs not right the way it is. I guess I would like to see something like thisà

In the place where you set your standings to a player, put a checkbox that disables a CONCORD response if that person damages you. This would let people in gangs work together with less risk and make dueling easier.

In suicide gank situations, IF the victim loses his ship, the insurance money for the gankers CONCORDed ship should go to their victim. Scale back the CONCORD response a bit to make it somewhat easier to actually high sec pirate as compensation.

If the victim isnÆt destroyed then CONCORD should just show up and lock down the offender for a few minutes. During that time the victim should have the option to tell CONCORD to either punish the offender by destroying his ship or to let him go.

Accidental shootings wouldnÆt be automatically fatal. You could gang with trusted friends without being paranoid of being accidentally CONCORDed and high sec gankings would be less profitable.

---

Originally by: Eralus

---

If other players destroy you because of a mistake and convoluted game mechanics, that's them being better than you are.

But when the game itself destroys you based on a mistake and convoluted game mechanics, that's just poor design.

A non-hostile act should NOT become hostile based on the action of ANOTHER party.

---

Originally by: Cipher7

---

Originally by: yarrmarr

---

useless troll.

Seems to me the repping victim got concorded the moment his repper started the next cycle after the CNR became flagged. It shouldn't be that difficult (and probably a very nice gesture, highly appreciated by mission runners and high sec pvp'ers) to have the program do a check on the status of the target before the cycle initiates and have a warning pop up..

(and no Cipher7: you probably couldn't care less, but the majority of the people enjoy high sec mission running and such.(

---

Not trolling at all.

Exactly how much budget should be spent making the game even more idiot-proof than it already is?

At what point do we expect players to have enough common sense not to stick their fingers into wall sockets?

Its like those people that eat Preparation H and sue the company, then the company has to spend money printing warning labels "CAUTION : DO NOT EAT THIS CREME."

Almost every product now has warning labels, there's a warning on Vinyl Caulk that you're not supposed to ingest it. Well gee, I'm glad they told us that.

Remember the days when death weeded the terminally stupid out of our societies?

Now warning labels keep those same stupid people alive.

And now they've come here, to Eve, to demand warning labels in-game to keep them from losing CNR's to the digital version of eating Preparation H.

---

Originally by: WulfWestphal

---

Edited by: WulfWestphal on 10/07/2007 11:53:13
Edited by: WulfWestphal on 10/07/2007 11:33:48

Originally by: PHPR Ronin

---

I'm not asking for an additional pop up. I'm asking for an existing pop up to work properly. If my client is already set to prompt before dangourous acts to occur and I'm stupid enough to fire on a say a station in high sec then I fully agree that i should loose any ship i'm flying as I was given the option and still said "sure, fire"

---

so you want that popup "you are performing a criminal action ... bla bla" when the next cycle of your repper would repair a now criminal target? i can understand it in the light of the things that happend to you.

but, eve is pretty much idiot proof by now. there are very little things that dont require you to close a little nasty warning window. its getting annoying, and the thought that someone complained enough or was stupid enough (and then complained) or even stayed uninformed enough with months of playtime on their back, is not making it better.

so im entering lowsec? thanks for the info, i saw that on the map and set the autopilot on shortest route. i am attacking a lone miner in a hisec area? its illegal and concord would be on their way? ya rly?? yeah i see that im selling for -50% profit, it is stated there in red. i can read, thanks...

putting more warning windows in, or letting the existing ones pop up more often, is not the solution i think. it treats symptoms not the source. concord, their actions and the options in gangs should be looked at. till then, be carefull what modules you activate, dont autotarget back, dont put them on autorepeat in empire and gee... use your brains more often.

p.s.: on a side note: im frequently in gangs with friends from another corp. remote repper, repper drones, sensor links, target links, etc. and till now only one domi from a friend was destroyed due to an autotarget back and a targetpainter. :) it never happend again, cause he learned and now we laugh that he put himself in the egg even before we went in the extravaganza... :)

edit: the threadtitel ist still stupid and insulting...

edit2: i want a warning window when i leave the station without accepting the mission from the agent (happens way to often) oh... and when having agressiontimer in lowsec and i attempt to warp to a gate (happend 2 times and never again) ... yeah sometimes **** happens *g*

---

Originally by: Thanos Draicon

---

Originally by: PHPR Ronin

---

It's confirmed that this is indeed a bug but since server logs don't log enough information to prove it, they deny it's occurrence.

---

Yes, I'm sure it's a big conspiracy because a GM was envious of your battleship, and wanted to deny it from you. Trust no one! Blame the Smoking Man!

---